NE-2520: Enable Gateway API tests on vSphere and baremetal by gcs278 · Pull Request #30946 · openshift/origin

gcs278 · 2026-03-31T21:57:57Z

Enable Gateway API e2e tests to run on vSphere and baremetal by conditionally skipping tests that require LoadBalancer services or managed DNS. Also fix test retry logic and skip tests on IPv6/dual-stack clusters where OLM catalog sources are typically unavailable.

Motivation

Support for NE-2286 - promoting GatewayAPIController to GA requires 7 days of feature gate test coverage. Running these tests on vSphere/baremetal provides additional platform coverage.

Changes

Platform capability detection

Add test-scoped variables managedDNS and loadBalancerSupported to track platform capabilities
Allow vSphere, baremetal, and EquinixMetal platforms (previously only cloud platforms)
Add isDNSManaged() helper to check for DNS zone configuration
Make assertions conditional based on platform capabilities:
- assertGatewayLoadbalancerReady() - only if loadBalancerSupported
- assertDNSRecordStatus() - only if managedDNS
- assertHttpRouteConnection() - only if both features available
- Skip entire deletion/recreation test if features missing
Update checkGatewayStatus() to wait for appropriate condition:
- Accepted=True on platforms without LoadBalancer (e.g., vSphere)
- Programmed=True on platforms with LoadBalancer (AWS, GCP, etc.)

Bug fixes for test reliability

Fix immediate test failures in poll retry loops (4 locations):
- CatalogSource check (line 313-314)
- ClusterServiceVersion check (line 345)
- HTTPRoute status checks (lines 892, 1017)
- Changed from o.Expect(err).NotTo(o.HaveOccurred()) to graceful error handling with retry
- Previously tests failed immediately on "NotFound" instead of retrying for up to 20 minutes

IPv6/dual-stack cluster handling

Add isIPv6OrDualStack() helper to detect IPv6/dual-stack networking via ServiceNetwork CIDRs
Skip Gateway API tests on IPv6/dual-stack clusters (any platform)
Reason: OLM catalog sources are typically disabled on baremetal IPv6/dual-stack clusters, preventing OSSM operator installation
Platform-agnostic detection replaces previous AWS-only dual-stack check

Behavior on vSphere/baremetal

What runs:

GatewayClass creation and acceptance ✅
Gateway creation (reaches Accepted=True) ✅
HTTPRoute creation and attachment ✅
OSSM/Istio integration tests ✅

What is skipped:

LoadBalancer service validation (no external IP available on vSphere/baremetal)
DNS record validation (no DNS zones configured on some platforms)
HTTP connectivity tests (requires both LoadBalancer + DNS)
LoadBalancer/DNS deletion and recreation test
All tests on IPv6/dual-stack clusters (catalog sources unavailable)

openshift-ci-robot · 2026-03-31T21:58:00Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

coderabbitai · 2026-03-31T21:58:06Z

Walkthrough

Adds runtime cluster-capability detection and conditional test behavior to Gateway API controller tests: detects load-balancer and managed-DNS support, skips IPv6/dual-stack clusters, adapts gateway creation/readiness checks and assertions, and replaces platform skip logic with capability discovery (loadBalancerSupported, managedDNS).

Changes

Cohort / File(s)	Summary
Gateway API Controller Tests `test/extended/router/gatewayapicontroller.go`	Introduced per-test capability discovery via `checkPlatformSupportAndGetCapabilities(oc) (bool,bool)`; added helpers `isDNSManaged` and `isIPv6OrDualStack`. Replaced `skipGatewayForUnsupportedPlatform` with capability checks. Added `loadBalancerSupported`/`managedDNS` flags computed in `BeforeEach`. Updated signatures: `createAndCheckGateway(..., loadBalancerSupported bool)` and `checkGatewayStatus(..., loadBalancerSupported bool)`. Gateway readiness now awaits `GatewayConditionProgrammed` when LB is supported, otherwise `GatewayConditionAccepted`. Conditionalized LB/DNS-related assertions and test skips. Reworked polling/logging: API Get errors are logged and retried (OLM CatalogSource/CSV/HTTPRoute reads and HTTPRoute/assertHttpRouteSuccessful polling) instead of immediate failures. Updated timeouts, error messages, and logging to reflect expected conditions.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-ci · 2026-03-31T21:58:13Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

openshift-ci · 2026-03-31T21:58:14Z

@gcs278: The label(s) /label kind/test cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, verified, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/skip-dependent-bug-check, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

Summary

Enable Gateway API e2e tests on vSphere by handling LoadBalancer provisioning and unmanaged DNS scenarios.

Changes

Add vSphere to supported platforms - requires MetalLB for LoadBalancer services

Add isDNSManaged() helper - detects if cluster has DNS zones configured

Skip DNS assertions on unmanaged platforms - avoids waiting for DNSRecord status

Direct IP connectivity - uses Gateway IP address when DNS is not managed

Follows the pattern from cluster-ingress-operator PR #1342.

Testing

vSphere Coverage (~70%):

✅ GatewayClass, Gateway, HTTPRoute creation

✅ LoadBalancer service and HTTP connectivity

⏭️ DNSRecord validation (skipped on unmanaged DNS)

Prerequisites: MetalLB configured on vSphere cluster

Related

NE-2529: DCM E2E Tests

Follow-up: CI job configuration in openshift/release

/label kind/test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-ci-robot · 2026-04-01T01:37:42Z

@gcs278: This pull request references NE-2520 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Enable Gateway API e2e tests to run on vSphere by conditionally skipping tests that require LoadBalancer services or managed DNS.

Motivation

Support for NE-2286 - promoting GatewayAPIController to GA requires 7 days of feature gate test coverage. Running these tests on vSphere provides additional platform coverage.

Changes

Add test-scoped variables managedDNS and loadBalancerSupported to track platform capabilities

Allow vSphere platform in skipGatewayIfNonCloudPlatform()

Add isDNSManaged() helper to check for DNS zone configuration

Make assertions conditional based on platform capabilities:

assertGatewayLoadbalancerReady() - only if loadBalancerSupported

assertDNSRecordStatus() - only if managedDNS

assertHttpRouteConnection() - only if both features available

Skip entire deletion/recreation test if features missing

Update checkGatewayStatus() to wait for appropriate condition:

Accepted=True on platforms without LoadBalancer (e.g., vSphere)

Programmed=True on platforms with LoadBalancer (AWS, GCP, etc.)

Behavior on vSphere

What runs:

GatewayClass creation and acceptance ✅

Gateway creation (reaches Accepted=True) ✅

HTTPRoute creation and attachment ✅

OSSM/Istio integration tests ✅

What is skipped:

LoadBalancer service validation (no external IP available)

DNS record validation (no DNS zones configured)

HTTP connectivity tests (requires both LoadBalancer + DNS)

LoadBalancer/DNS deletion and recreation test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-04-01T02:01:23Z

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

gcs278 · 2026-04-01T02:47:01Z

Opfh i forgot we need to test vsphere tech preview too:
/test e2e-vsphere-ovn-techpreview

gcs278 · 2026-04-01T02:48:01Z

Is this how to kick it off?
/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-techpreview

openshift-ci · 2026-04-01T02:48:08Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/336b0030-2d75-11f1-968e-6fa8157092ad-0

rikatz · 2026-04-01T11:48:09Z

test/extended/router/gatewayapicontroller.go

+		switch platformType {
+		case configv1.AWSPlatformType, configv1.AzurePlatformType, configv1.GCPPlatformType, configv1.IBMCloudPlatformType:
+			loadBalancerSupported = true
+		case configv1.VSpherePlatformType:


nit: I would probably join both vsphere and default case here, or even just start with loadBalancerSupported = false and change it in case platform is GCP, AWS, Azure or IBMCloud

rikatz · 2026-04-01T11:50:04Z

test/extended/router/gatewayapicontroller.go


+// isDNSManaged checks if the cluster has DNS zones configured (public or private).
+// On platforms like vSphere without external DNS, DNS records cannot be managed.
+func isDNSManaged(oc *exutil.CLI) bool {


recovering from a previous review you did on my PR :)

https://github.com/openshift/cluster-ingress-operator/pull/1342/changes#diff-9c27a40de3f83386ac43ec91cac5d70c860cf9b53bcc2098056676a69697f207R697-R709

Is the Private or Public not being null enough for it? I think for this case right now it may be, but though was worth asking

Logically it makes sense: in order for DNS to work we need either a private or public zone listed. And correct, this logic is mirroring what we did in CIO E2E. That's had some exposure and seems to work well.

rikatz · 2026-04-01T12:00:23Z

None of my comments are blockers

/lgtm
/approve
/hold
Unhold as you wish or if you feel a strong desire to fix my nit comments, otherwise we can move

gcs278 · 2026-04-01T21:55:00Z

/testwith openshift/installer/main/e2e-aws-ovn-dualstack-ipv6-primary-techpreview #30946

openshift-ci · 2026-04-01T21:55:06Z

@gcs278, testwith: could not generate prow job. ERROR:

no ref for requested test included in command. The org, repo, and branch containing the requested test need to be targeted by at least one of the included PRs

gcs278 · 2026-04-01T22:00:24Z

maybe i need to have a openshift-installer PR that is a NO-OP?

/testwith openshift/installer/main/e2e-aws-ovn-dualstack-ipv6-primary-techpreview openshift/installer#10453

rikatz · 2026-04-01T22:12:10Z

/lgtm

openshift-ci · 2026-04-01T22:13:37Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gcs278, rikatz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~test/extended/router/OWNERS~~ [gcs278,rikatz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

gcs278 · 2026-04-01T22:14:17Z

/test e2e-metal-ipi-ovn

openshift-ci-robot · 2026-04-02T02:44:57Z

@gcs278: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

Here is my evidence that I'm not going to break vsphere and metal jobs:

My payload results show the following tests passing (or not failing with GWAPI-related failures):

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv4: b12693d3-8bd7-4ba9-8d2c-f0e1bd83bf14

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6: d5e6e0e6-d84b-42fb-8d69-112a023de7e5

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-dualstack: 9b9d6c84-fe71-478d-a008-b5f5e022176c

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-dualstack-techpreview: b72f0a99-6e8d-4d3f-840e-a39caf7d1f4b

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-techpreview: 6ab6364d-933a-4ff1-bfde-499da119bfc5

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-serial: 3fe46e7a-ab33-42b9-8bf5-bf0f1e1ace2a

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-techpreview: f24417c8-1977-44f8-b92a-86725c7f81c4

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-upi: d36dbedc-4e6f-4bde-804e-55870f9f3e14

Installer Team also has a pre-submit e2e-aws-ovn-dualstack-ipv6-primary-techpreview which I confirmed the Gateway API tests were still being skips (ref NE-2422: Skip Gateway API tests on dual-stack clusters #30942).

Pre-submit have been passing as well

/verified

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

gcs278 · 2026-04-02T02:46:08Z

Here is my evidence that I'm not going to break vsphere and metal jobs:

My payload results show the following tests passing (or not failing with GWAPI-related failures):
- periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv4: b12693d3-8bd7-4ba9-8d2c-f0e1bd83bf14
- periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6: d5e6e0e6-d84b-42fb-8d69-112a023de7e5
- periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-dualstack: 9b9d6c84-fe71-478d-a008-b5f5e022176c
- periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-dualstack-techpreview: b72f0a99-6e8d-4d3f-840e-a39caf7d1f4b
- periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-techpreview: 6ab6364d-933a-4ff1-bfde-499da119bfc5
- periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-serial: 3fe46e7a-ab33-42b9-8bf5-bf0f1e1ace2a
- periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-techpreview: f24417c8-1977-44f8-b92a-86725c7f81c4
- periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-upi: d36dbedc-4e6f-4bde-804e-55870f9f3e14
Installer Team also has a pre-submit e2e-aws-ovn-dualstack-ipv6-primary-techpreview which I confirmed the Gateway API tests were still being skips (ref NE-2422: Skip Gateway API tests on dual-stack clusters #30942).
Pre-submit have been passing as well

/verified by ci

openshift-ci-robot · 2026-04-02T02:46:20Z

@gcs278: This PR has been marked as verified by ci.

Details

In response to this:

Here is my evidence that I'm not going to break vsphere and metal jobs:

My payload results show the following tests passing (or not failing with GWAPI-related failures):

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv4: b12693d3-8bd7-4ba9-8d2c-f0e1bd83bf14

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6: d5e6e0e6-d84b-42fb-8d69-112a023de7e5

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-dualstack: 9b9d6c84-fe71-478d-a008-b5f5e022176c

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-dualstack-techpreview: b72f0a99-6e8d-4d3f-840e-a39caf7d1f4b

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-techpreview: 6ab6364d-933a-4ff1-bfde-499da119bfc5

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-serial: 3fe46e7a-ab33-42b9-8bf5-bf0f1e1ace2a

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-techpreview: f24417c8-1977-44f8-b92a-86725c7f81c4

periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-upi: d36dbedc-4e6f-4bde-804e-55870f9f3e14

Installer Team also has a pre-submit e2e-aws-ovn-dualstack-ipv6-primary-techpreview which I confirmed the Gateway API tests were still being skips (ref NE-2422: Skip Gateway API tests on dual-stack clusters #30942).

Pre-submit have been passing as well

/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

gcs278 · 2026-04-02T02:47:47Z

/unhold

openshift-ci-robot · 2026-04-02T02:48:38Z

@gcs278: This pull request references NE-2520 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Enable Gateway API e2e tests to run on vSphere and baremetal by conditionally skipping tests that require LoadBalancer services or managed DNS. Also fix test retry logic and skip tests on IPv6/dual-stack clusters where OLM catalog sources are typically unavailable.

Motivation

Support for NE-2286 - promoting GatewayAPIController to GA requires 7 days of feature gate test coverage. Running these tests on vSphere/baremetal provides additional platform coverage.

Changes

Platform capability detection

Add test-scoped variables managedDNS and loadBalancerSupported to track platform capabilities

Allow vSphere, baremetal, and EquinixMetal platforms (previously only cloud platforms)

Add isDNSManaged() helper to check for DNS zone configuration

Make assertions conditional based on platform capabilities:

assertGatewayLoadbalancerReady() - only if loadBalancerSupported

assertDNSRecordStatus() - only if managedDNS

assertHttpRouteConnection() - only if both features available

Skip entire deletion/recreation test if features missing

Update checkGatewayStatus() to wait for appropriate condition:

Accepted=True on platforms without LoadBalancer (e.g., vSphere)

Programmed=True on platforms with LoadBalancer (AWS, GCP, etc.)

Bug fixes for test reliability

Fix immediate test failures in poll retry loops (4 locations):

CatalogSource check (line 313-314)

ClusterServiceVersion check (line 345)

HTTPRoute status checks (lines 892, 1017)

Changed from o.Expect(err).NotTo(o.HaveOccurred()) to graceful error handling with retry

Previously tests failed immediately on "NotFound" instead of retrying for up to 20 minutes

IPv6/dual-stack cluster handling

Add isIPv6OrDualStack() helper to detect IPv6/dual-stack networking via ServiceNetwork CIDRs

Skip Gateway API tests on IPv6/dual-stack clusters (any platform)

Reason: OLM catalog sources are typically disabled on baremetal IPv6/dual-stack clusters, preventing OSSM operator installation

Platform-agnostic detection replaces previous AWS-only dual-stack check

Behavior on vSphere/baremetal

What runs:

GatewayClass creation and acceptance ✅

Gateway creation (reaches Accepted=True) ✅

HTTPRoute creation and attachment ✅

OSSM/Istio integration tests ✅

What is skipped:

LoadBalancer service validation (no external IP available on vSphere/baremetal)

DNS record validation (no DNS zones configured on some platforms)

HTTP connectivity tests (requires both LoadBalancer + DNS)

LoadBalancer/DNS deletion and recreation test

All tests on IPv6/dual-stack clusters (catalog sources unavailable)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

gcs278 · 2026-04-02T02:53:09Z

Ah I think I have to trigger the pipeline
/pipeline required

openshift-ci-robot · 2026-04-02T02:53:13Z

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

openshift-ci-robot · 2026-04-02T02:55:37Z

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

openshift-ci-robot · 2026-04-02T02:55:41Z

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

openshift-ci · 2026-04-02T06:55:57Z

@gcs278: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-fips	`974a80c`	link	true	`/test e2e-aws-ovn-fips`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-trt · 2026-04-02T06:59:43Z

Job Failure Risk Analysis for sha: 974a80c

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi	High [Jira:Node][sig-node] Node non-cnv swap configuration should reject user override of swap settings via KubeletConfig API [OCP-86395] [Suite:openshift/conformance/parallel] This test has passed 100.00% of 12 runs on release 5.0 [Architecture:amd64 FeatureSet:default Installer:upi JobTier:standard Network:ovn NetworkStack:ipv4 OS:rhcos9 Owner:eng Platform:vsphere Procedure:none SecurityMode:default Topology:ha Upgrade:none] in the last week.

lihongan · 2026-04-02T06:59:56Z

/test e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview

We are going to promote the GatewayAPIWithoutOLM feature gate right? I think we need run -techpreview job to ensure coverage.

lihongan · 2026-04-02T07:10:34Z

/payload-job e2e-metal-ipi-ovn-ipv6-runc-techpreview e2e-vsphere-ipi-ovn-runc-techpreview e2e-vsphere-static-ovn-techpreview

openshift-ci · 2026-04-02T07:10:37Z

@lihongan: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

e2e-metal-ipi-ovn-ipv6-runc-techpreview
e2e-vsphere-ipi-ovn-runc-techpreview
e2e-vsphere-static-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0b673830-2e63-11f1-8873-2caffaeddc18-0

openshift-merge-bot · 2026-04-02T07:20:18Z

/retest-required

Remaining retests: 0 against base HEAD b578433 and 2 for PR HEAD 974a80c in total

lihongan · 2026-04-02T07:47:26Z

sorry payload job name were wrong

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-runc-techpreview periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ipi-ovn-runc-techpreview periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-static-ovn-techpreview

openshift-ci · 2026-04-02T07:47:33Z

@lihongan: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-runc-techpreview
periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ipi-ovn-runc-techpreview
periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-static-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/32270310-2e68-11f1-81af-3fc0071989a2-0

lihongan · 2026-04-02T11:41:50Z

OK, the 5 GatewayAPIWithoutOLM tests passed in one payload job https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30946-nightly-4.22-e2e-vsphere-static-ovn-techpreview/2039610683523338240

: [sig-network-edge][OCPFeatureGate:GatewayAPIController][Feature:Router][apigroup:gateway.networking.k8s.io] [OCPFeatureGate:GatewayAPIWithoutOLM] Ensure GatewayClass contains CIO management conditions after creation [Suite:openshift/conformance/parallel]
: [sig-network-edge][OCPFeatureGate:GatewayAPIController][Feature:Router][apigroup:gateway.networking.k8s.io] [OCPFeatureGate:GatewayAPIWithoutOLM] Ensure GatewayClass contains sail finalizer after creation [Suite:openshift/conformance/parallel]
: [sig-network-edge][OCPFeatureGate:GatewayAPIController][Feature:Router][apigroup:gateway.networking.k8s.io] [OCPFeatureGate:GatewayAPIWithoutOLM] Ensure Istio CRDs are managed by CIO and istiod deployment exists [Suite:openshift/conformance/parallel]
: [sig-network-edge][OCPFeatureGate:GatewayAPIController][Feature:Router][apigroup:gateway.networking.k8s.io] [OCPFeatureGate:GatewayAPIWithoutOLM] Ensure Sail operator resources are not installed [Suite:openshift/conformance/parallel]
: [sig-network-edge][OCPFeatureGate:GatewayAPIController][Feature:Router][apigroup:gateway.networking.k8s.io] [OCPFeatureGate:GatewayAPIWithoutOLM] Ensure istiod Deployment contains the correct label [Suite:openshift/conformance/parallel]

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 31, 2026

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026

gcs278 force-pushed the enable-gateway-api-vsphere branch 2 times, most recently from 217a875 to d09911f Compare April 1, 2026 01:24

openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 1, 2026

gcs278 changed the title ~~Enable Gateway API tests on vSphere with unmanaged DNS support~~ Enable Gateway API tests on vSphere with conditional feature checks Apr 1, 2026

gcs278 marked this pull request as ready for review April 1, 2026 01:33

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 1, 2026

openshift-ci bot requested review from jcmoraisjr and knobunc April 1, 2026 01:34

gcs278 force-pushed the enable-gateway-api-vsphere branch from d09911f to 667ab93 Compare April 1, 2026 01:36

openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 1, 2026

gcs278 force-pushed the enable-gateway-api-vsphere branch from 667ab93 to 0a85364 Compare April 1, 2026 01:37

gcs278 changed the title ~~Enable Gateway API tests on vSphere with conditional feature checks~~ NE-2520: Enable Gateway API tests on vSphere with conditional feature checks Apr 1, 2026

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 1, 2026

rikatz reviewed Apr 1, 2026

View reviewed changes

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 1, 2026

openshift-ci bot assigned rikatz Apr 1, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 1, 2026

gcs278 mentioned this pull request Apr 1, 2026

DO NOT MERGE: E2E testing openshift/installer#10456

Closed

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 1, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 2, 2026

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 2, 2026

openshift-merge-bot bot merged commit e0e704f into openshift:main Apr 2, 2026
25 checks passed

gcs278 mentioned this pull request Apr 6, 2026

NE-2520: Promote GatewayAPIWithoutOLM to GA openshift/api#2772

Open

Conversation

gcs278 commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation

Changes

Platform capability detection

Bug fixes for test reliability

IPv6/dual-stack cluster handling

Behavior on vSphere/baremetal

Uh oh!

openshift-ci-robot commented Mar 31, 2026

Uh oh!

coderabbitai bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

openshift-ci bot commented Mar 31, 2026

Uh oh!

openshift-ci bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Testing

Related

Uh oh!

openshift-ci-robot commented Apr 1, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation

Changes

Behavior on vSphere

Uh oh!

openshift-ci-robot commented Apr 1, 2026

Uh oh!

gcs278 commented Apr 1, 2026

Uh oh!

gcs278 commented Apr 1, 2026

Uh oh!

openshift-ci bot commented Apr 1, 2026

Uh oh!

rikatz Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

rikatz Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

gcs278 Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

rikatz commented Apr 1, 2026

Uh oh!

gcs278 commented Apr 1, 2026

Uh oh!

openshift-ci bot commented Apr 1, 2026

Uh oh!

gcs278 commented Apr 1, 2026

Uh oh!

rikatz commented Apr 1, 2026

Uh oh!

openshift-ci bot commented Apr 1, 2026

Uh oh!

gcs278 commented Apr 1, 2026

Uh oh!

openshift-ci-robot commented Apr 2, 2026

Uh oh!

gcs278 commented Apr 2, 2026

Uh oh!

openshift-ci-robot commented Apr 2, 2026

Uh oh!

gcs278 commented Apr 2, 2026

Uh oh!

openshift-ci-robot commented Apr 2, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation

Changes

Platform capability detection

Bug fixes for test reliability

IPv6/dual-stack cluster handling

Behavior on vSphere/baremetal

gcs278 commented Mar 31, 2026 •

edited

Loading

coderabbitai bot commented Mar 31, 2026 •

edited

Loading

openshift-ci bot commented Mar 31, 2026 •

edited

Loading

openshift-ci-robot commented Apr 1, 2026 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Apr 2, 2026 •

edited by openshift-ci bot

Loading